Network operating system client architecture for mobile user equipment

ABSTRACT

A network operating system agent can operate to facilitate communications to a network device and a managing server of self-organizing network devices to exchange contexts between an application managed by a user equipment device and the network device. Relationships between self-organizing devices and applications of a user equipment device can be extended so that the network devices are context aware of the application settings. In response to detecting the user equipment device communicating via the network devices, a set of user equipment device parameters and a set of application settings of the application can be communicated to the network devices. The application settings can be modified according to the a set of radio network performance settings of the self-organizing network devices with the user equipment device based on the set of user equipment device parameters and the set of application settings of the application.

CROSS-REFERENCE TO RELATED APPLICATIONS

The subject application is a continuation of, and claims priority toeach of, U.S. patent application Ser. No. 15/423,547 (now U.S. Pat. No.9,948,511), entitled “NETWORK OPERATING SYSTEM CLIENT ARCHITECTURE FORMOBILE USER EQUIPMENT,” and filed on Feb. 2, 2017, which is acontinuation of U.S. patent application Ser. No. 14/049,991 (now U.S.Pat. No. 9,565,576), entitled “NETWORK OPERATING SYSTEM CLIENTARCHITECTURE FOR MOBILE USER EQUIPMENT,” and filed on Oct. 9, 2013. Theentirety of the above noted application is incorporated herein byreference.

TECHNICAL FIELD

The subject disclosure relates to wireless communications and, inparticular, to network operating system client architecture for mobileuser equipment.

BACKGROUND

The use of mobile devices and the resulting mobile traffic continuesgrowing at a very fast pace and the trend shows no signs of stopping. Tomeet the mobile traffic growth and improve the end user experience,mobile service providers are actively looking for mechanisms to improvenetwork efficiency, system capacity, and end user experience by costeffectively leveraging all radio network technologies, includingcellular and Wi-Fi technologies. The routing of network traffic to aWi-Fi radio and to a cellular radio, for example, can affect the userexperience. For example, if the network traffic is routed to a networkthat is not appropriate for that network traffic, it can result in lossof the communication (e.g., dropped calls), poor services, and othernegative impacts to the user experience.

To ensure customer satisfaction, wireless service providers aim todeliver a high quality service at any location, to facilitate reliableand efficient mobile communications. Consumers can access a growingnumber of networks using a mobile device. These networks include, forexample, 3G networks, 4G networks, long-term evolution networks andWi-Fi networks. These networks allow consumers to communicate voice,text, multimedia, and other data to and from other network entities,such as servers and other mobile devices.

BRIEF DESCRIPTION OF THE DRAWINGS

Various non-limiting embodiments are further described with reference tothe accompanying drawings in which:

FIG. 1 illustrates an example, non-limiting wireless communicationsenvironment that can be utilized with the disclosed aspects;

FIG. 2 illustrates an example, non-limiting system for establishingcommunications with network devices and applications of UE devices,according to an aspect;

FIG. 3 illustrates an example, non-limiting network operating systemagent kernel, according to an aspect;

FIG. 4 illustrates an example, non-limiting implementation of a networkcontrol manager architecture for a user equipment device, according toan aspect;

FIG. 5 illustrates an example, non-limiting system for networkcommunications between communications networks applications of a UEdevice, according to an aspect;

FIG. 6 illustrates an example, non-limiting method for routing networktraffic, according to an aspect;

FIG. 7 illustrates an example, non-limiting method, according to anaspect;

FIG. 8 illustrates another example, non-limiting method, according to anaspect;

FIG. 9 is a schematic example wireless environment that can operate inaccordance with aspects described herein;

FIG. 10 illustrates a block diagram of access equipment and/or softwarerelated to access of a network, in accordance with an embodiment; and

FIG. 11 illustrates a block diagram of a computing system, in accordancewith an embodiment.

DETAILED DESCRIPTION

Aspects of the subject disclosure will now be described more fullyhereinafter with reference to the accompanying drawings that illustratedifferent example embodiments. In the following description, forpurposes of explanation, numerous specific details are set forth inorder to provide a thorough understanding of the various embodiments.However, the subject disclosure can embody many different forms andshould not be construed as limited to the example embodiments set forthherein.

The management of current relationships between the applications managedby user equipment (UE) devices (e.g., mobile devices) and the differentnetworks that the UEs travel through is not complete. For example,mobile applications are network blind, and networks are applicationblind, such that the mobile application settings are not controlled ormodified by the networking operations and vice versa. A need thereforeexits to apply an innovative Self Organizing Network (SON) approachbetween the applications managed by UEs and the self-organizing networkdevices through a Network Operating System Agent (NOSA), or otherwiseindicated as a NOSA kernel, a NOSA manger and the like, which canoperate to establish and manage relationships between the applicationand network behaviors.

In one embodiment, the application and network relationships can extendbeyond just the radio access network and Quality of Service (QOS), andcan comprise mechanisms for self-organized approaches to diversify datadelivery, self-organizing control considerations based on UE parameters.For example, current general purpose operating systems do not operate tocouple network level self-organizing and performance managementfunctions between the self-organizing network devices and the UEapplications functionally managed by the UE, which can also operatetogether with an external storage (e.g., a cloud storage) storing theapplication. The NOSA, however, operates to provide and separatemanagement of network bandwidth, load balancing, self-organizingfunctions, traffic monitoring probes, traffic time shifting, offloading,preloading functions, and network policy to the applications and UEsmanaging the applications from the networks.

The relationships between the applications and managing UEs with thenetwork devices can include any interactions for operating over anetwork managed by the network devices, such as a Wi-Fi network device,a macro cell network device, a micro cell network device, a Femto cellnetwork device, etc., and other corresponding networks of networkdevices. The relationships managed by the NOSA can be operationalfunctions between the self-organizing network devices and theapplications of the UE, which selectively operate based on UEparameters. For example, UE parameters can comprise UE sensed data, ordata detected with respect to the UE functions. For example, some UEparameters can comprise accelerometer data, battery power data, speeddata, directional data, and network observed signaling data, load data,and congestion data, or any other UE sensed data.

In another embodiment, the self-organizing network devices can includean innovative integrated storage blade that is communicatively coupledto a Radio Access Network (RAN) device and a mobile packet core as partof SON devices that can function to perform real time traffic profiling,analytics packet reprioritization, data time shifting and network storeand forward functions. The self-organizing network devices can provideand separate management of network bandwidth, load balancing,self-organizing functions, traffic monitoring probes, traffic timeshifting, offloading, preloading, and network policy to the applicationsand users.

To meet mobile traffic growth, one or more of the disclosed aspectsprovides a network architecture that enables selection of the bestavailable radio technology (from all available radio technologies,including cellular and Wi-Fi technologies) for user traffic deliveryaccording to the needs of applications managed on UEs. The networkselection can be a function of radio network conditions (radio networkperformance settings), user subscription profile, application settings,device mobility state (e.g., speed and pattern), application settings ona UE device, and so on, to improve network efficiency, provide therequested data delivery conditions for the application's demands. Thenetwork devices can provide data delivery conditions or options to thenetwork devices via the relationships managed by the NOSA with theapplications and according to various triggers communicated by theapplications because of such relationships. Further, the selection canprovide a consistent user experience across multiple types of userequipment, operating system, and original equipment manufacturer (OEM)manufactures and platforms. One or more of the disclosed aspects canalso provide Application Program Interfaces (APIs) that allow for thedevelopment of Access Network Discovery and Selection Function (ANDSF)carrier clients that can operate in conjunction with the self-organizingdevices through the NOSA.

In another embodiment, the UE device (e.g., mobile device) and/or theapplication(s) that the UE manages can make determinations related towhich radio network to use, what the QOS will be, when to use that radionetwork, and under what conditions or triggers to route or have routedthe user traffic based on one or more attributes or conditions.Decisions can be based on one or more of the following: an ANDSF policy(e.g., 3GPP ANDSF capabilities, 4GPP capabilities, Wi-Fi networkcapabilities, user equipment intelligence, and the other networkcapabilities); cellular network congestion condition and parameters;Wi-Fi network congestion condition; and/or mobile device information,including battery usage, mobile device relative movement with respect toa Wi-Fi access point (e.g., speed, vibration, patterns), mobile devicerelative movement with respect to a cellular access point, other UEparameters discussed herein, and so on. In another embodiment, a UE caninteract with a kernel that operates as the NOSA that resides on the UE,or on as an external device operationally coupled to the UE, which caninstruct network devices on routing the user traffic to the selectedradio network device (e.g., Wi-Fi, Femto cell, Macro cell, Micro cell,etc.) or for certain radio network performance parameters or networkconditions, on a per application basis. The instructions can be combinedwith a user preference and the traffic routing functions can beperformed (e.g., binding user application/flow to a radio networkdevice) based in part on the combination of user preferences and networkconsiderations according to the self-organizing devices andcorresponding network conditions or radio network performance settings.Consequently, the UE device can comprise the client network operatingsystem or NOSA that can enable SON extension, wherein the UE deviceprovides appropriate context to the SON device or servers and policyengines.

As the mobile industry moves towards Giga speed applications, thenext-generation mobile packet cores could have the ability to automatethe traffic flow management that meets application demands on thenetworks. The mobile packet core can be a device that operates themanagement of the radio access network and network devices operating theradio access network, such as for providing sessions or informationexchanges, authentication, packet forwarding and like networkingoperations. The network devices herein can be a gateway support nodedevice, a cellular management entity device, or a packet data gatewaydevice for example, as well as other network devices functionallyserving network communications for UEs and combinations of these devicescommunicatively coupled to one another.

FIG. 1 illustrates an example, non-limiting wireless communicationsenvironment 100 in accordance with various embodiments described. Thewireless communications environment 100 can include a multitude ofwireless communications networks, each having a respective coveragearea. The coverage area of some of the wireless communications networkscan overlap such that one or more network devices can provide coverageareas or zones to UEs or mobile devices whose coverage areas fromdifferent networks of network devices overlap. The network devices canoperate with one another as a Self-Organizing Network (SON), in which atleast some of the network devices can be configured to provideself-configuration and self-optimizing capabilities that provide theability to automate certain operations, management functions and systemmanagement functions. The SON incorporates self-configuration,self-optimization, monitoring, and operation management to allow thenetwork devices to be communicatively coupled into the network andoperate with little to no human intervention while taking into accountapplication settings for applications operating on and managed by theUEs.

The wireless communications environment 100 includes one or morebroadcast servers 102, 104 (e.g., cellular servers) and one or moreWi-Fi access points 106, 108 deployed within the wireless communicationsenvironment 100 and servicing one or more UE devices 110, 112, 114, 116,118. Each wireless communications network (e.g., broadcast servers 102,104 and Wi-Fi access points 106, 108) comprises one or more networkdevices (e.g., a set of network devices) that operate in conjunctionwith one another in order to process network traffic for the one or moreUE devices 110, 112, 114, 116, or 118. For example, the broadcastservers 102, 104 can comprise a set of network devices that are cellularenabled network devices, which could provide different network speeds(e.g., 2G, 3G, 4G, etc.). In another example, the Wi-Fi access points106, 108 can include a set of network devices that are Wi-Fi enableddevices.

The communications environment 100 can include one or more managementservers 130, 132 that are communicatively coupled to the network devicessuch as the broadcast servers 102, 104 as a control-node for one or morenetworks. The management servers 130, 132 can operatively control UEdevice tracking and paging procedures including retransmissions. Themanagement servers 130, 132 can control, for example, the beareractivation/deactivation process and choosing a serving gateway for theUE devices 110, 112, 114, 116, or 118 at the initial attach and at thetime of an intra-network handover (e.g., Wi-Fi to 3G, 3G to 3G or thelike). The management servers 130, 132 can authenticate UEs byinteracting with the other devices communicatively coupled theretoand/or sets of data servers such as a home subscriber server and thelike. The management servers 130, 132 can operate in conjunction withone or more mobile packet core components having a processors and memorythat can operate to generate and allocate temporary identities to UEsand terminates Non-Access Stratum (NAS) signaling or other signalingprotocol layer. The NAS can be used to manage the establishment ofcommunication sessions (e.g., between UEs) and for maintainingcontinuous communications with the user equipment as it moves. Themanagement servers 130, 132 can also manage signaling to the AccessStratum for carrying information over the wireless portion of thenetwork and security key management operations (e.g., authentication,verification, authorization operations) with UE application data and UEdevice functions. In particular, the network devices can operatetogether with the UEs to provide and separate management of networkbandwidth, load balancing, self-organizing functions, traffic monitoringprobes, traffic time shifting, offloading, preloading, and networkpolicy to the applications and UEs managing the applications.

As illustrated, each of the one or more Wi-Fi access points 106, 108 canhave a corresponding service area 120, 122. In addition, each of the oneor more broadcast servers 102, 104 can have a corresponding service area124, 126. However, the wireless communications environment 100 is notlimited to this implementation and various other architectures can alsobe employed. For example, the self-organizing network devices can deployany number of Wi-Fi access points and respective service areas withinthe wireless communications environment 100.

A UE device can contain some or all of the functionality of a system,subscriber unit, subscriber station, mobile station, mobile, wirelessterminal, device, mobile device, remote station, remote terminal, accessterminal, user terminal, terminal, wireless communication device,wireless communication apparatus, user agent, user device, or UE device.A mobile device or UE can be a cellular telephone, a cordless telephone,a Session Initiation Protocol (SIP) phone, a smart phone, a featurephone, a wireless local loop (WLL) station, a personal digital assistant(PDA), a laptop, a handheld communication device, a handheld computingdevice, a netbook, a tablet, a satellite radio, a data card, a wirelessmodem card and/or another processing device for communicating over awireless system. In addition, the UE devices 110, 112, 114, 116, 118 caninclude functionality as more fully described herein such as one or moreapplications such as application software or bundled software andhardware processors for a particular set of useful tasks beyond therunning of the computer itself. Examples can include accountingsoftware, enterprise software, graphics software, media players, officesuites and the like. An application, for example, can apply the power ofparticular a computing platform or system software to a particularpurpose.

In one aspect, cellular broadcast servers 102, 104 and Wi-Fi accesspoints 106, 108 can monitor and communicate with one or moreapplications on the UE and their surrounding radio conditions (e.g., byemploying respective measurement components). For example, each of thecellular broadcast servers 102, 104 and Wi-Fi access points 106, 108 candetermine network traffic load on its respective network by performing anetwork diagnostic procedure. As an example, during a network listenprocedure, cellular broadcast servers 102, 104 and Wi-Fi access points106, 108 can scan their radio environment to determine networkperformance statistics. Various parameters associated with cellularbroadcast servers 102, 104 and Wi-Fi access points 106, 108 can bedetected during the network diagnostic procedure, such as, but notlimited to, frequency bands, scrambling codes, common channel pilotpower, bandwidth across respective networks, universal mobiletelecommunications system terrestrial radio access receive signalstrength indicator, as well as application settings from the UE.

In an example scenario, networks can service UE devices 110, 112, 114,116, and 118 through one of the cellular broadcast servers 102, 104, orWi-Fi access points 106, 108. As a UE device travels within the wirelesscommunications environment 100, the respective UE device can move in andout of the coverage area of the associated serving network. For example,as a user is sending/receiving communications through their respectiveUE device, the user might be walking, riding in a car, riding on atrain, moving around a densely populated urban area (e.g., a largecity), wherein the movement might cause the mobile device to be movedamong various wireless communications networks. In such cases, it isbeneficial to route the network traffic (e.g., handoff) from a servingnetwork to a target network in order to continue the communication(e.g., avoid dropped calls). The routing, for example, can be dependenton one or more applications of a particular UE. The applications canhave application settings that can dictate a set of network protocolsand further comprise multiple different sets of network protocols basedon one or more triggers or events that initiate a corresponding set ofnetwork protocols. The managing servers 130, 132 and the core components134, 136 in conjunction with the other network devices of the SON canoperate network functions according to the application settings and theset of triggers corresponding to a particular set of network protocols.The applications of the UE can have different sets of applicationsettings, which can have priorities or a prioritization scheme based onone or more event triggers for operation of the application.

For example, as a driver enters a Wi-Fi area data, sharing or datatransfer can transfer over to a Wi-Fi network according to theapplication settings for an application that is operating on the UE. Adata transfer can occur based on an event or trigger, as discussedabove, so that an application that requires a function with greaterspeed for data transfer could switch to a 4G network instead for aspecified time period until the function is triggered to pause by a settrigger or event specified in the application settings. The datatransfer could be stopped and made to continue automatically once aresponse from a particular party, UE, network device, or the like isreceived. The response or vote could operate as a trigger designated bythe application settings. Multiple devices (e.g., UEs or other devices)can then share the information via the SON automatically subsequent tothe SON devices performing an aggregation of the data. The data shared,for example, can be dependent on a different trigger and a different setof application settings or network protocols, which can be designatedautomatically by the application or the user manually via theapplication.

Depending on location, UE devices 110, 112, 114, 116, 118 can have theoption to connect to any number of networks based on the applicationsettings, for example. In one scenario, one of the cellular broadcastservers 102, 104 can service all the UE devices 110, 112, 114, 116, 118,which can cause excessive load on the respective cellular broadcastserver and cause UE devices 110, 112, 114, 116, 118 to have apotentially negative user experience. The application settings couldhave a request for a data transfer or collection of data from one ormore other UE devices. The application settings could indicate to theself-organizing devices of the network environment a desire for dataspeeds that are on one network, but not another. The settings couldestablish certain time-periods for a set of application settings to takeeffect, such as certain data speeds for the set time-period. Theapplication settings can also comprise set triggers or events to switchnetworks and further continue with data transfer, stop data transfer, orestablish data communication under different protocol priorities basedon UE parameters such as battery, speed, direction, and network observedsignaling, load, congestions and the like.

In another embodiment, UE devices 110, 112, 114, 116, 118 can connect toany available network based on real-time or near real-time networkcondition statistics and an intelligent network selection policy with aNetwork Operating System agent or kernel. In one example scenario, UEdevice 114 for example, can determine Wi-Fi access point 106 or Wi-Fiaccess point 108 offer a higher quality of experience and UE device 114can connect to the selected Wi-Fi access point based, in part, on anetwork selection policy or data diversity policy included withspecifications of the application settings. Further to this example, UEdevice 114 might determine cellular broadcast server 102 or cellularbroadcast server 104 offer a higher quality of experience and UE device114 can connect to the selected cellular broadcast server based, in parton the network selection policy designated by the application settings.According to another aspect, UE device 114 could split its communicationtraffic flows and use a selected Wi-Fi access point for a set ofcommunication traffic flows and a selected cellular broadcast server foranother set of communication traffic flows, based on the applicationsettings provided to the network.

In some situations, when an option is available where a particular UEdevice can be serviced by either a cellular broadcast server or a Wi-Fiaccess point, the Wi-Fi access point can be selected automatically basedon the application functioning requirements and as specified by theapplication settings of an application on the UE. For example, the UEdevice might have user preferences established within a particular setof application settings to occur at one event trigger (e.g., datasharing, delivery, UE sensed data, etc.), which indicates that when aWi-Fi network is available, network traffic of the UE device should berouted to the Wi-Fi network. Another set of application settingsassociated with the same application could occur for another ordifferent event trigger. Such application settings could vary betweenapplications on a UE and for various trigger events that could occur.For example, certain application settings could establish a networkspeed or type of network because, in some cases, there is no associatedcost to the user of the UE device when a Wi-Fi network is utilized, ascompared to usage of a cellular network. Thus, the network traffic ofthe UE device could be automatically routed to the Wi-Fi network,regardless of the load on the Wi-Fi network and/or other considerations,which could result in a negative user experience (e.g., droppedcommunications, poor communications, and so on).

However, according to some aspects discussed herein, rather thanautomatically connecting to a Wi-Fi access point, other considerationscan be utilized to route the network traffic of the UE device to theWi-Fi network, or to determine that the network traffic should remain onthe cellular network and/or move to a different cellular network orWi-Fi network. For example, instead of moving to the Wi-Fi networkautomatically when the Wi-Fi network is available, a comparison is madebetween the Wi-Fi network and a cellular network. If the Wi-Fi networkis more congested than the cellular network, the user traffic of the UEdevice can be routed to the cellular network. However, if it isdetermined that the Wi-Fi network is not as congested as the cellularnetwork (or both networks have about the same level of congestion), theuser traffic of the UE device can be routed to the Wi-Fi network.

According to various aspects discussed herein, a UE device cancontinuously, periodically, or based on other temporal conditions,receive data indicative of network statistics (e.g., network policy,traffic load or congestion on the network, capability of the network,and so on) according to the application requirements at the time. Asnetwork performance changes, a UE device can determine that at least aportion of its respective network traffic should be routed to adifferent network. The determination can be made based on real-time, ornear real-time, network statistics.

In accordance with one implementation, a kernel serving as the NOSA canbe implemented with the UE or external to a UE to facilitate communicateof application settings for an application managed by the UE to thenetwork devices. The network devices can then initiate policies andbased decisions such as handover, network conditions and load conditions(e.g., network congestion) based on the application settings. Thenetwork devices of the SON, for example, can take a self-organizingapproach to diverse data delivery, self-organizing controlconsiderations based on UE observed accelerometers, battery power,speed, direction, and network observed signaling, load, and congestions.A portion of these parameters can be communicated as part of theapplication settings in order to set corresponding limits or triggersfor defining the particular needs of the application, providing thestatus of the UE and for prioritizing data delivery options between theUE and the SON.

In accordance with an implementation, a UE device can be configured toperform dynamic intelligent network selection per service provided basedon a combination of an access network discovery and selection functionpolicy, network conditions, and intelligence associated with the UEdevice. For example, the UE device can autonomously determine under whatconditions to route network traffic and to which network (e.g., Wi-Firadio or cellular radio) the network traffic should be routed on a perapplication basis (e.g., by splitting traffic flows). The decision canbe made in such a manner that the decision has a positive impact on theuser experience.

The access network discovery and selection function policy can bereceived from a network server that can be configured to push (e.g.,broadcast) the information to one or more UE devices based on theapplication settings communicated or received by the network devices.The network selection policy can include logic that can instruct the UEdevice to select a network based, at least in part, on networkstatistics, which can include network conditions and load conditions(e.g., network congestion), or policies based on the UE parameters suchas UE observed accelerometers, battery power, speed, direction, andnetwork observed signaling, load, and congestions. According to someimplementations, one or more network collection agents can monitormultiple networks and can periodically, continuously or repeatedlypush/communicate updated network statistic information to the UE device.Such periodic and/or continuous updates can enable real-time or nearreal-time knowledge of the network conditions by the UE device and couldfurther be implemented in response to one or more event triggersselected by or assigned to the application of the UE device.

Further, according to the various aspects described herein, the networkselection can be based, in part, on an operator policy drivenintelligent network selection and traffic steering capability based onthe network conditions and the UE device intelligence that offersoptimal (or as close to optimal as possible) and consistent userexperience across all UE/operating system (OS)/original equipmentmanufacturer (OEM) platforms and manufactures.

A network can include a plurality of elements that host logic forperforming tasks on the network. The logic can be hosted on servers,according to an aspect. In packet-based wide-area networks, servers canbe placed at several logical points on the network. Servers may furtherbe in communication with databases and can enable communication devicesto access the contents of a database. Billing servers and applicationservers are examples of such servers. A server can include severalnetwork elements, including other servers, and can be logically situatedanywhere on a service provider's network, such as the back-end of acellular network, and managed by the packet core components 134, 136. Aserver hosts or is in communication with a database hosting an accountfor a user of a mobile device. The “user account” includes severalattributes for a particular user, including a unique identifier of themobile device(s) owned by the user, relationships with other users,application usage, location, personal settings, business rules, bankaccounts, and other information.

FIG. 2 illustrates an example, non-limiting system 200 for establishingcommunication relationships between applications for a UE device andnetwork devices, according to aspects described. System 200 can beimplemented, for example, on a UE device 201 or be distributedthroughout a set of self-organizing network devices in communicationwith the UE device. System 200 comprises at least one memory 202 thatcan store computer executable components and instructions. System 200can also include at least one processor 204, communicatively coupled tothe at least one memory 202. Coupling can include various communicationsincluding, but not limited to, direct communications, indirectcommunications, wired communications, and/or wireless communications.The processor 204 can facilitate execution of the computer executablecomponents stored in the at least one memory 202. The at least oneprocessor 204 can be directly involved in the execution of the computerexecutable component(s).

System 200 can comprise various components that can integrate with oneor more UE device as an internal component, externally as network deviceor as a virtual component. The system 200, for example, can comprise anevaluation manager 206 that can be configured to compare one or moreparameters associated with two or more wireless networks and furtherevaluate UE device parameters that comprise UE sensed data (e.g.,accelerometer data, battery power data, speed data, direction data,network observed signaling data representing a signaling of the set ofself-organizing network devices, load data representing a load of theset of self-organizing network devices, and congestion data representinga congestion of the set of self-organizing network devices).

According to one implementation, parameters associated with a firstnetwork can be compared to parameters associated with a second networkand/or a parameters associated with subsequent (e.g., third, fourth)networks. The network parameters can further comprise the UE parametersthat can be utilized for optimizing the application settings, selectinga set of application settings, the network device to UE device relationsand providing network delivery options for data based on the parametersdetected on the network and the UE. For example, the one or moreparameters associated with the communications networks can includecongestion conditions, network parameter conditions, or applicationconditions (e.g., event triggers such as predefined time-periods,location designations, network performance, the type of network, orother triggers). According to an aspect, the one or more parameters caninclude network load information. In accordance with another aspect, theone or more parameters can include bandwidth utilization of the network(e.g., 3G, 4G, long term evolution, and so on). Other parameters caninclude peak usage times, available bandwidth of a network, a number ofrequests received by a network resource, as well as other metrics orparameters, which can be specified certain events or functions for datadelivery via one or more different sets of application settings of theUE device managed application.

In an implementation, a first wireless network can include networkdevices that are cellular enabled device (e.g., a cellular network) anda second wireless network can include network devices that are Wi-Fienabled devices (e.g., a Wi-Fi network). Parameters related to thecellular networks can include cellular network congestion condition andparameters received through cell broadcast or a system informationblock(s). Dynamic cellular conditions include load information, signalstrength thresholds, and/or subscriber profile based offset to signalstrength threshold percentages. Parameters related to the Wi-Fi networkscan include Wi-Fi network access point conditions, such as BSSI loadcondition, RSSI, and WAN metrics and/or performance measurements overthe Wi-Fi network.

The evaluation manager component 206 can also be configured to comparethe one or more network parameters, associated with the two or morewireless networks, with one or more parameters associated with the userequipment device. The one or more parameters of the user equipmentdevice can include usage information (e.g., applications being executed(e.g., running) on the user equipment device). The parameters can alsoinclude a movement parameter of the user equipment device. The movementparameter can relate to whether the user equipment device is stationaryor moving and, if moving, a speed at which the device is being movedand/or a direction to which the device is being moved. The speed and/ordirection of the device can be analyzed with respect to a location of acellular network and/or a Wi-Fi network, according to an implementationand provided to the self-organizing network devices, which can enablecertain data delivery options according to the UE parameters and theapplication settings as a set of radio network performance settings. Forexample, if the user equipment device is being moved toward a network,that network might be favored over a network that the device is beingmoved away from, or not directly headed toward. A trigger, for example,could be designated in the application settings as well, such asswitching to a Wi-Fi network device coverage when within a certaindistance of the coverage area, stopping data delivery, or continuingdata delivery upon entering the coverage area. In an example, speedand/or movement of the device can be determined based on a vibrationpattern of the device. Other parameters can include user preferencesand/or settings associated with the selection of a network for routingof network traffic. Further parameters can include a battery usageand/or remaining battery capability (e.g., battery life).

Also included in system 200 is a selection manager component 208 thatcan be configured to determine which radio technology (and associatedset of network devices) should be chosen such that at least a portion ofthe network traffic of the user equipment (also referred to as usertraffic) is routed to the selected network (e.g., by a routing managercomponent 210). For example, the comparison performed by the evaluationmanager component 206 can produce various possible results. For example,a first possible result can be that at least a portion of the networktraffic of the user equipment device should be routed to a first set ofnetwork devices (e.g., a first set of target devices), which areassociated with a first radio technology (a first set of radio networkperformance settings). Further, a second possible result can be that theportion of the network traffic (or another portion of network traffic)of the user equipment device should be routed to a second set of networkdevices (e.g., a second set of target devices), which are associatedwith a second radio technology (e.g., a second set of radio networkperformance settings).

The system 200 can further include a selection manager component 208that operates to make determinations for policy considerations. Thedetermination performed by selection manager component 208 can complywith a network selection policy received from a network device thatcurrently provides a service to the user equipment device (e.g., a setof source devices). In an implementation, complying with the networkselection policy can include observing discovery information andselection policies of the serving network (e.g., set of servingdevices). The discovery information can relate to one or more trafficrouting rules established by the serving network. According to someimplementations, instructions related to the network selection policy(e.g., how to route the user traffic) can be combined with theapplication settings set by the application or the user in order for theselection manager component 208 to make the network determination.

The application settings can include trigger events that are designatedby the application, a user of the UE managing the application, orselected from a set of triggers provided by the network device, whichcould vary depending upon location or other UE parameters or UE senseddata, such as bandwidth requirements, location, speed, direction oftravel, etc., as discussed above. For example, a cellular network 220(3G, 4G, etc.) or a Wi-Fi network 222 can be chosen as a result of thecellular network condition when combined with the Wi-Fi condition forthe determination based on the application requirements or set ofapplication settings specifying the requirements. The applicationsettings can enable the application to perform one or more operations byestablishing context aware relationships between the UE applications andset of self-organizing network devices. For example, if the cellularnetwork is loaded (e.g., high congestion) and the Wi-Fi network is notcongested, under that condition, the Wi-Fi network can be chosen.However, if the cellular network is not congested and also the Wi-Finetwork is not congested, the cellular network might be chosen, or notchosen depending upon one or more applications settings or UEparameters. Thus, the decision is made in part based on a comparison ofboth the networks and the context awareness of the application of the UEand UE.

The routing manager component 210 can be configured to route one or moreportions of the network traffic of the user equipment device to the setof network devices chosen by the selection manager component 208. Forexample, the routing manager component 210 can be configured to changefunctionality of the user equipment device from a cellular connectivityfunction to a Wi-Fi connectivity function. In another example, therouting manager component 210 can be configured to change thefunctionality of the user equipment device from a Wi-Fi connectivityfunction to a cellular connectivity function. The routing managercomponent 210 is configured to perform the appropriate signaling betweena source network and the target network to enable seamless handoff orrouting of the user network traffic.

According to an implementation, the routing manager component 210 isconfigured to route a first set of network traffic of the user equipmentdevice (e.g., a first set of traffic flows) to a first network and toroute a second set of network traffic of the user equipment device(e.g., a second set of traffic flows) to a second network. For example,a cellular network might be congested and, therefore, some of thetraffic of the user equipment device can be kept on (or routed to) a LTEnetwork, for example. At the same time, a media application or videosharing application might be executing on the user equipment device andthis set of traffic can be routed to (or kept on) a Wi-Fi network. Insuch a manner, different sets of traffic flows of the user equipmentdevice can be split, wherein some of the traffic flows are routed to acellular network while other traffic flows are routed to a Wi-Finetwork. Such splitting of the traffic flows can be determined based inpart, on the network policy, such as a network selection policy, forexample, or the application settings, such as a price structure,performance requirements, or some other set of triggers. The triggerscan be selected, set or modified by the UE or the network and can becommunication to the network devices or SON from a selected set ofapplication settings from the UE application to the network devices viathe NOSA or operating kernel of the NOSA 216 at the UE, external orvirtually through the network.

The NOSA kernel 216 can be configured to operate as a manager in alow-level abstraction layer for input/output requests from theapplications being managed by the UE to the self-organizing networkdevices. The NOSA kernel 216 can be operatively connected to the UEoperating system and is specialized for network operations andcommunications to the SON in order to provide network awarerelationships for application functions. The NOSA kernel 216, forexample, translates the application context (e.g., processes,interruptible tasks, threads of the application) to the network context(processes, interruptible tasks, threads of the network) to account forthem in processing data delivery with the managing server and mobilepacket core components of the set of self-organizing devices. The NOSA216 can operate with the self-organizing devices to communicate anddetermine data delivery operations such as time-sharing, load balancing,resource allocation, time shifting of packet flows, cache operations,data packet segmentation and reassembly, and caching functions. The UEdevice can comprise the client network operating system or NOSA kernel216 that can enable SON extension, wherein the UE device providesappropriate context to the SON device or servers and policy engines withapplication policies or settings on the UE device.

The system 200 further comprises an application services and applicationprogramming interface manager (API) 218. The application services andAPI manager 218 operates to manage underlying flow state information,information to manage dynamic pricing or billing, and integrate properinterfaces to manage micro shift data delivery. The application servicesand API manager 218 can further provide virtual service portals for newQuality of Experience (QOE) dependent business models, enable analyticand knowledge dashboards to applications on the UE device, and createpersonalized flow models and policy-based services for users, businessesand internal optimization tools. The application services and APImanager 218 can communicate data with the NOSA kernel 216 to monitorcycle times, fallouts, end-to-end flow rates and quality of experienceto make determinations of application settings to communicate to the SONdevices 212, 214, for example. These components enable optimum qualityof experience to UE devices and applications managed or controlled bythe UE devices with network devices. The device component operativelycommunicate advantageously to eliminate manual configuration ofequipment at the time of deployment, right through to dynamicallyoptimizing application and radio network performance during operation,which increases alternative service offers for large data deliveries inwireless networks.

FIG. 3 illustrates an example, non-limiting NOSA kernel 216 forgenerating close relationships between self-organizing network devicesand applications of UEs to make the SON devices context aware. The NOSAkernel 216 can be implemented on a user equipment device, operate one anexternal device, a network device, or a cloud network. The NOSA kernel216 comprises an operation system (OS) and device agnostic abstractioncomponent 302, an application and NOSA network component 304, a networkservices component 306, a control manager application and context awarecomponent 308, a control manager services and API component 310, acontrol manager extension component 312, an core control manager kernel314 and a wireless system on a chip adaptation component 316. Thesecomponents of the NOSA kernel 216 illustrates an example architecturefor the NOSA kernel 216 to operate as a manager in a low-levelabstraction layer for establishing relationships between theapplications being managed by the UE to the self-organizing networkdevices.

The operation system (OS) and device agnostic abstraction component 302is configured to operate as a manager for the operation system and theUE device context (tasks, threads, process etc.) and the networkcontext. For example, network routing processes can be a set of contextthat comprises a different number of communication layers, each of whichare responsible for handling some part of the end-to-end communication.Each layer, for example, can be tasked with a specific job or set ofprocessing tasks, receives input from the OS, the device or the network,and produces output in a predetermined fashion. The operation system(OS) and device agnostic abstraction component 302 enables thecommunication of the context for the OS, the UE, and the network amongthe self-organizing network devices and different layers of the NOSAkernel 216.

The application and NOSA network component 304 is configured tocommunicate a suite or set of tools for the applications operating onthe UE for communicating (e.g., displaying in a display or interfacingwith applications) various application settings and enabling sets ofapplication settings for performance parameters, functions and the likewith triggers or events. For example, one set of application settingscan indicate a power level threshold, a congestion level, a time shift,a priority level for a network bandwidth, offloading triggers, packetprioritization, network store and forwarding functions, and the likesettings. Additionally, another set of application settings can bestored or configured to have different levels of each of these settings,different thresholds, or different triggers to instantiate theapplication settings with the self-organizing network devices.Consequently, the application and the network relationships can becontext aware of one another and interact with communications that takeinto account the application settings and network conditions. Thus, theapplication settings can be communicated to the network devices and theUE device to be configured, modified or set based on the currentconditions of the networks and the application functions associated withthe settings.

The network services component 306 is configured to communicate networkdelivery options that can comprise current network conditions such asavailable networks to the application processes and managing UE devicebased on the current UE parameters and network conditions. For example,UE parameters (e.g., accelerometer data, battery power data, speed data,directional data) can be considered as trigger events for modifying ordetermining the optimal application settings by which the applicationnot only operates on, but indicates to the network that it is eithercapable of operation with or will operate with. In cases in which atrigger is not met, the application could halt or stop certainfunctions, wait or continue processing with a different setting. Thenetwork conditions taken into account as the network delivery optionscan include congestion, network observed signal among devices forservices conducted or provided by the devices, load data, congestiondata. In response to the triggers that are met, a set of applicationsettings can be communicated and implemented by a radio access networkdevice, a managing server, a mobile packet core, or other network deviceto perform the application set real-time traffic profiling, analyticpacket reprioritization, data time shifting and network store, forwardfunctions, etc.

In addition, the network services component 306 can operate tocommunicate event triggers than a network device of the networkenvironment could provide. These network provided triggers could beselected and stored in the application settings for a UE device toselect from or set as the condition by with a network is chosen or bywhich some other application setting or parameter of the UE is made tooperate in conjunction with network. For example, a San Fran networkcould trigger operation with a 3G network, a different Wi-Fi network, amicro cell network, a Macro cell network, a priority scheme, a datadelivery scheme, etc. based on any event such as a geographical locationfrom one building floor to another, one restaurant or another, oneapplication function or another as initiated by the UE device and thelike event triggers.

The control manager application and context aware component 308 isconfigured to modify a set of application settings of the user equipmentdevice by changing particular settings (network type, bandwidth, speed,event triggers etc.) and a set of radio network performance settings ofthe set of self-organizing network devices with the user equipmentdevice based on the set of user equipment device parameters. This can bedone automatically or manually based on network conditions (largecongestion, lack of or not of storage functioning, time shifting,loading and congestion policies specific to a network device or notspecific, etc.). The control manager application and context awarecomponent 308 can select a network delivery option as a preferredsetting, which can include settings available for the network toprovide. The application as a result of a defined trigger can tag setsof application settings by which the control manager application andcontext aware component 308 implements the delivery options to meet orexceed the particular application settings tagged for the event trigger.In addition, where a delivery option (data delivery option) is not ableto meet or exceed an application setting, the control managerapplication and context aware component 308 can make a determinationwhether the application functioning would except a different datadelivery option, set a different trigger (e.g., a wait period, or thelike) or halt the application processes. The UE device functions canalso be taken into consideration, in which application settings of otherapplications running could be affect depending on the hardwarelimitations and make similar determinations.

The control manager application and context aware component 308 canoperate receive one or more inputs to communicate for network andapplication setting determinations. For example, an input can be aservice provider access network discovery and selection function policy,which can be received through an S14 interface, for example, or othernetwork communication interface. The access network discovery andselection function policy can include, according to an implementation,the access network discovery selection function capabilities andenhancements, for example, such as network conditions and user equipmentdevice intelligence.

In addition, the control manager application and context aware component308 can operate to facilitate determinations of data delivery optionsavailable and application settings for electronic Multimedia BroadcastMulticast Services (MBMS) or other similar services that enable apoint-to-multipoint interface specification for existing and upcomingcellular networks, for delivery specifications for efficient delivery ofbroadcast and multicast services, both within a cell as well as withinthe core network. For broadcast transmission across multiple cells, theeMBMS or other like service specification can define transmission viasingle-frequency network configurations, for example.

The control manager application and context aware component 308 canfurther integrate or factor in determinations according to theimportance of managing (monitoring as well as actively managing)networked applications for Quality of Experience (QOE), which caninclude various metrics such as availability, Mean Time to Repair(MTTR), and Mean Time Between Failures (MTBF) for networkingapplications managed by the UE devices. Transportation tracking andcontext operations can determine the tracking conditions based on the UEparameters discussed above. Video streaming and Voice over Long TermEvolution (LTE) networks or Internet Protocol (IP) can be monitored andselected in a determination for data delivery options. In addition,security options and applications can be considered with third partycontrol manager applications or other NOSA kernel applications, and autocertification operations of application communications and processes,such as communication certification and security. The control managerapplication and context aware component 308 can further determinecontext for flow policies and application frameworks for applications aspart of determining application settings, such as prioritization,congestion and bandwidth considerations for selecting a data deliveryoption. As discussed above, the selection manager component 208 (of FIG.2) utilizes the access network discovery and selection function policyto perform selection of a radio network (e.g., a radio technology) orprovide for such as an application setting together with the otherfunctioning components discussed above.

The control manager services and API component 310 can be configured tomonitor and process event synchronizations, in which more than one eventcan be synchronized across application settings, delivery options forradio network device settings of the self-organizing devices to preventconflict. As discussed above, event triggers can be determined, providedas selection for setting, modifying or canceling within applicationsettings. The triggers can be provided by the SON devices for selection,manually set, and modified for particular application settingsassociated with different applications or subsets of applicationsettings that can be tagged with certain events.

The control manager services and API component 310 can further implementvideo codecs, video share processes, radio options, Broadcast,multicast, pricing algorithms according to the network data deliveryoptions or radio network settings for such options, roaming manageractivities, caching structures such as Network Access Storage in supportof cross layer designs and applications and speech services, forexample. The control manager services and API component 310 can furtheroperate to extend carrier services from various network carriers withthe above mention services, for example.

The manager extension control component 312 can be configured to supportcore management extensions between applications and the network devicessuch as for different implementations and applications. For example,mobile health can be supported via the network and UEs and be bridged onthe network for receiving high priority or less priority within theapplication settings for data delivery with health services andinformation, as well as with security and emergency functions. Differentcommunication protocols can also be implemented with certainapplications with the network devices of the SON with the controlmanager extension component 312, such as Zigbee, Bluetooth, Vehicularcommunications, etc. Other networks and their communication protocolscan be considered based on an application setting that can be broadbandwide-area networks such as cellular networks, local-area networks,wireless local-area networks (e.g., Wi-Fi), and personal area networks,such as near-field communication networks. Communication across anetwork can be packet-based; however, radio and frequency/amplitudemodulation networks can enable communication between communicationdevices using appropriate analog-digital-analog converters and otherelements. The manager extension control component 312 can furtheroperate to perform QOE monitoring, adaptive network services anddatabase process controlling such as with Lite DB or other databaseengines in communication with the network via the NOSA kernel 216 basedon application communicated request or settings.

The core control manager kernel 314 can operate to provide microkernelinterfaces among the OS and UE device, multi core processing operationsfor specific applications and high speed data delivery, fast booting,power state monitoring and controlling based on UE parameters andapplication needs, instant channel access activations for emergency orother needs. Event notification can be controlled for indicating eventsto the user and further along to the network devices as the UEinterprets events as occurring. The core control kernel manager 314 canfurther interpret and communicate a resource manager framework engine.For example, cross layer functions can be implemented for manuallypairing between two devices, in timing, radio, network relationshipstates, resources and network discoveries. QOS can be guaranteed or madeuniform at both ends of the devices or multiple Oss, such as operationwith appropriate thresholds for VOLTE, for example, or otherapplications and their specific sets of settings. Reactions or responsescan be set in the application settings for network devices fordegradation of voice with reserved bandwidths that can be utilized at aper cell level, for example.

The wireless system on a chip adaptation component 316 can be configuredto implement various network integrations with the NOSA kernel 216 to beable to provided network and application relationships across differentnetworks such as in different countries or different communicationentities or proprietary entities.

As provided herein, the disclosed aspects enable dynamic intelligentnetwork selection per service provider policy based on a combination ofan access network discovery and selection function, network conditions,UE device intelligence, and application settings of one or moreapplications managed by one or more UEs.

Referring now to FIG. 4, illustrated is an example system 400 thatestablishes connecting relationships between self-organizing networkdevices and applications 414 of UE devices detected by the SON devices.Included in system 400 is an intelligent selection function 402 (ISfunction) that preforms different operating functions to determinenetwork selection decisions as to which radio access network, when,under what conditions network traffic (of the user equipment device)should be routed, what radio network settings should be established, andapplication settings 416 for optimizing application functions, which arebased on different types of input. In order to perform these functions,a connection manager 418 aggregates data from different network devicesand the UE device. The connection manager 418 operates as the NOSA orNOSA kernel discussed above, for example. Examples of informationreceived at the UE device include radio network settings such as networkcongestion conditions, network bandwidth, load balancing data,self-organizing functions, traffic monitoring probe data from trafficmonitoring probes, traffic time shifting, offloading, preloading andnetwork policy data to the applications 414 of the UE device and the UEdevice. Examples of information generated by the UE device include usageinformation, movement data, accelerometer data, battery power, speeddata, direction data, and network observed signaling.

For example, the connection manager 418 can operate to receive a serviceprovider access network discovery and selection function (ANDSF) policy,which can be received by an ANDSF policy 404 (ANDSF function). Theservice provider ANDSF can be received through an S14 interface 406 forexample. The ANDSF policy 404 can include, according to animplementation, the 4GPP ANDSF capabilities and enhancements, such asnetwork conditions (load, probe data, congestion, bandwidth, etc.), aswell as other network conditions (3GPP, Wi-Fi, etc. from the SONdevices. The selection manager component 208 (of FIG. 2) utilizes theANDSF policy 404 to perform selection of a radio network device for anetwork to connection with or application settings 416 to be receivedvia a network delivery option. The selection manger component 208 canreceive UE device intelligence to make determinations for selecting setsof application settings 416 and radio network settings such as aparticular type of network, bandwidth, storing, speed, etc.

The connection manager 418 can communicate cellular network congestionconditions, UE parameter data by a cell broadcast (CB)/systeminformation block (SIB) function (illustrated as CB/SIB function 408).The CB/SIB function 408 can be a cellular network intelligent functionon the user equipment device that receives and/or extracts variousdynamic cellular network condition(s) and/or parameter(s) from thecellular network. A cellular network condition, for example, can relateto load information, which can be in the format of a load flag andreceived from one or more monitoring probes communicated by the UEdevice via the connection manager 418. For example, the load flag can becolor-coded (e.g., red, yellow, green, and so forth) to indicate theamount of network traffic (e.g., load) on that particular cellularnetwork. In another example, another manner of indicating the loadinformation on the cellular network can be utilized (e.g., a pie chart,a line chart, based on a number of lights illuminated, and so on).

Another cellular network condition can relate to signal strengththresholds. For example, a signal strength threshold is a referencesignal received power (RSRP) over the reference signal subcarriers, in along-term evolution (LTE) implementation. In another example, a signalstrength threshold can be a reference (received) signal code power(RSCP) in a universal mobile telecommunications system (UMTS)implementation.

A network profile can relate to a subscriber profile based on an offsetto signal strength thresholds or a profile of application settingscomprising different subsets of application settings ranked according topriority to a corresponding application on the UE. For example, a UEdevice associated with a first signal strength threshold can be rankeddifferently than another UE device associated with a second signalstrength threshold based on different application settings for anoperating application respectively. In an implementation, the variousthresholds can be associated with different colors. For example, thefirst signal strength threshold and a second signal strength thresholdof different users can be coded for different priorities, as well asdifferent application settings tagged for implementations according todifferent event triggers or different priorities depending on the radionetwork settings or conditions of a network profile.

Another cellular network condition or profile can be a load condition ora percentage of bandwidth that can be used to move portions or sets ofthe user equipment devices between cellular networks and Wi-Fi networks.For example, a threshold level of a number or percentage of users thatcan be adequately serviced by a particular network could be utilized.According to this implementation, when the threshold level or thresholdpercentage is reached (or almost reached), no new user equipment devicesmight be routed to that network until the amount of user equipmentdevices serviced by the network is below the threshold level. In anexample, the percentage can be indicative of a congestion percentage(e.g., based on total available bandwidth, used bandwidth, or capablebandwidth verses used bandwidth).

Another input can be a Wi-Fi network congestion condition and one ormore Wi-Fi network parameters, illustrated as a Wi-Fi function 410. TheWi-Fi function 410 can relate to a Wi-Fi network condition function onthe user equipment device that receives and/or extract Wi-Fi accesspoint conditions. One condition can be a basic service set (BSS) loadcondition. Another condition can be a received signal strength indicator(RSSI). A further condition can be wireless access node (WAN) metricsvia HotSpot2.0. Another condition can be a performance measurement overthe Wi-Fi network, which can include round trip time (RTT) delay,jitter, packet loss, and so on.

The CB/SIB function 408 and the Wi-Fi function 410 represent networkinformation 412. Such network information can be utilized by theevaluation manager component 206 (of FIG. 2) to perform networkcomparisons based on the application settings 416 and UE parameters 415of the UE device. For example, the network information is utilized withthe information obtained related to the user equipment device and theapplication settings 416 to perform the comparison and therebycommunicate data delivery options among the network device resources ofthe SON devices for application functions. In cases in which theapplication settings 416 correspond to a particular set of applicationsettings 416 and are not able to receive the resources for anapplication function, the application function can be halted for a timedperiod or the application settings can be modified to another set ofapplication settings for the application function. In addition oralternatively, other application functions could be selected or providedas options in a dashboard or interface control to the UE device.

A further input for determining application and network settings for theUE applications over various network devices among SON networks can beuser equipment device intelligence. Such information can includeapplications 414 executing on the user equipment device. For example,some applications might be better served by a cellular radio (e.g.,cellular network), while other applications might execute well on eithercellular networks or Wi-Fi networks. The same applies for variousbandwidths, speeds, storage configurations, security policies, crosslayer QOS and feedback loops with the devices and applications at large,billing policies, load and congestion policies and other data deliveryoptions that are scalable or not with Quality Control Bits (QCB), inwhich different applications or sets of application settings could bedifferent for these data conditions based on upon the specificrequirements and/or data triggers that are tagged to the applicationsettings on the UE devices. If an application executing on the userequipment device might not function properly on a Wi-Fi network, thedecision to route the network traffic to the Wi-Fi network might bedelayed and/or disabled, based on a trigger event, and then possiblyreinitiated based on another trigger event. In another example, trafficflows might be split so that some traffic flows utilize the Wi-Finetwork while other traffic flows utilize the cellular network oranother network device, (Macro, Micro Femto cell device).

Another input can include user preferences. For example, a userpreference might be to route the network traffic to a Wi-Fi networkwhenever a Wi-Fi network is available. Such user preference is takeninto consideration when a determination is made whether (or not) toroute the network traffic to a Wi-Fi network. In some instances, thetraffic will not be routed to the Wi-Fi network even though the Wi-Finetwork is available and is preferred by the user (e.g., userpreference). These user preferences can be part of the applicationsettings, in which the settings for a billing scheme are entered toprovide Wi-Fi access for VoIP calling when the UE device is within anarea of coverage or for data delivery options such as communicatingother data for sharing, aggregating and delivering on Wi-Fi versus acellular network device. With faster speeds required, a 4GPP optioncould be a data delivery option or a radio network performance settingthat is indicated or selected according to the application settings.Other examples and scenarios as this can also be envisioned withdifferent networks, speeds, bandwidths, policies and other considerationdiscussed herein with the applications of a UE, the application settingsof the corresponding applications, and the radio network settings for adiversity of data delivery options.

A connection manager 418 can be included as a portion of the userequipment device operating system (OS 420), such as the NOSA kerneldiscuss above. The connection manager 418 can comprise instructions oractions on how to route user traffic to the proper radio (e.g., Wi-Firadio or cellular radio) on a per application basis (e.g., as a functionof the applications 414 executing, or expected to be executed, on theuser equipment device), by splitting the traffic flows. It is noted thatthe term “connection manager” can refer to any entity that performs atraffic routing function (e.g., such as a routing manager component210). The connection manager 418 also communicates applicationrequirements (settings) for an application from the UE device and radionetwork settings as data delivery options from the set of SON devices ornetwork environment, in which the UE finds itself. For example, theconnection manager represents an entity that binds user application/flowto a radio network and further bridges connections there-between as akernel, for example, among the OS kernels. The connection manager can bea native connection manager, a connectivity engine, or the like.

User equipment device intelligence can relate to intelligent networkselection (e.g., INS function 402), which can relate to variousinformation that can be known (or generated) internal to the userequipment device. Such intelligence can include battery usage level(e.g., amount of battery life remaining, statistics as to the amount ofbattery being consumed for various applications and/or programsexecuting on the user equipment device, and so on). Another example ofuser equipment device intelligence relates to the user equipment devicerelative movement to the Wi-Fi access point. The relative movement caninclude speed, vibration patterns, and so on. For example, relativemovement can relate to whether the user equipment device is stationaryor is moving and, if moving, the speed at which the user equipmentdevice is being moved. In another example, the relative movement canrelate to a direction that the user equipment device is being movedrelative to the locations of the various radio networks. Thisinformation can be received from the connection manager 418, illustratedat 424, according to an aspect.

As discussed above, the “connection manager” is a generic term thatrefers to an entity, such as the NOSA kernel discussed above, whichtakes the input from the user preference and operator intelligentnetwork selection instruction and performs a traffic routing function.For example, the connection manager can bind user application/flow andsettings to a radio (e.g., cellular radio 426 and/or Wi-Fi radio 428)and radio network settings. The connection manager can be a nativeconnection manager, a connectively engine, or the like.

FIG. 5 illustrates an example, non-limiting system 500 for managingnetwork functions to applications of UE devices, according to an aspect.System 500 includes a memory 202 and a processor 204 operativelyconnected to the memory 202. A NOSA manager component 501 can operate asa managing kernel that is communicatively couple to the OS of the UEdevices and configured to compare various parameters of one or morecommunications networks 502 with various parameters of a UE device andapplications 522 managed by the UE device. NOSA manager component 501can be operatively connected to a transceiver component 504 that can beconfigured to receive the various parameters (radio network settings)from the one or more communications network devices 502 (e.g., SONnetwork devices) and communicate UE parameters aggregated by the UEparameter component 526 and applications settings 524 of the application522.

For example, each communications network of the one or morecommunications networks 502 can monitor parameters related to networkcongestion and/or other network parameters. According to animplementation, the parameters can include, but are not limited to,traffic load over the network, and available bandwidth of the network.Other parameters can include, but are not limited to, signal strengththresholds, received signal strength indications, subscriber profilebased offset to signal strength thresholds percentage, speed, bandwidth,data time shifting, network storage, real time traffic profiling,analytics packet reprioritization, and/or forward functions.

The NOSA manager component 501 can comprise various components toestablish tight relationships with the UE device operation system andnetwork devices such as the core components (e.g., mobile core component503) and the serving network 503, which operates as a managing server.The NOSA manager component 501 can comprise an analysis component 512, apolicy component 514, a tagging component 516, a probe component 518, adata delivery component 520, and a UE parameter component 526 formanaging and facilitating close relationships between the networkdevices of a SON network environment and applications 522 managed by aUE device on the network.

Transceiver component 504, or another system 500 component, can beconfigured to obtain network selection policy information for a servingnetwork 506, (e.g., from a network device that provides a service to theuser equipment device). The network selection policy information caninclude discovery information and selection policies of the servingnetwork 506.

For example, the serving network 506 can comprise an access networkdiscovery and selection function server 508 that can utilize networksecurity techniques to communicate securely with a selected group ofuser equipment devices. For example, access network discovery andselection function server 508 can authenticate select user equipmentdevices, application functions on the UE device, and allow only thoseuser equipment devices or applications that are serviced by a particularservice provider to communicate with the access network discovery andselection function server 508. Further, access network discovery andselection function server 508 can utilize secure channels, encodedchannels, encrypted channels, and the like to perform communicationswithin a wireless network environment.

Access network discovery and selection function server 508 can createand determine network traffic steering rules (or routing rules). Thenetwork traffic steering rules can be created for individual userequipment devices or for groups of user equipment devices andimplemented based on the application 522 requirements, UE parametersascertained by the UE parameter component 526, or the network resourcesand policies available to the application 522. In one or moreimplementations, access network discovery and selection function server508 can create group network traffic steering rules for groups of userequipment devices based on, for example, subscription profiles, qualityof service agreements, user equipment device type, user equipment devicecapabilities, application specific policies and resources, and so on.

According to an implementation, a network traffic steering rule caninclude instructions to guide a user equipment device in connection withradio access network selection or provided to the application 522 forimplementing settings according to the rules, policies and resourcescommunicated from that serving network that are available with themobile core component 503. For example, a traffic steering rule caninclude instructions for radio access network selection, or radionetwork settings based on network load condition, mobility states, userequipment device hardware metrics or parameters, user equipment deviceperformance metrics, application settings 524 and so on. The selectionsand network settings can be communicated to the transceiver component504 in order for the NOSA manager component 501 to enable applicationfunctions to be implemented with the application 522 according to theapplication settings 524. Additionally or alternatively, the NOSAmanager component 501 can modify the application settings 524 to operateunder different conditions than the settings specified or configured inthe application 522. Thus, the NOSA manager component 501 can operate todetect what the application 522 demands are from the network devices(communication network 502, mobile core component 503, serving network506) and enable the network to command what resources (data deliveryoptions) that the application is capable of performing with.

The application 522 can operate on a UE device (e.g., laptop, mobile, orcloud service, etc.). For example, the application 522 could be in thecloud network or storage, in which a UE browser can facilitateoperation. The application 522, for example, can be a browser or anotherapplication 522 demanding data delivery. The application 522 cantranslate the user's request to some actionable network request. TheNOSA manger component 501 operates to extending the network to agents ornetwork OS agents that can handle activities (e.g., data delivery)demanded by the application 522.

The mobile core component 503 (e.g., core back-end processor) cancomprise an integrated storage blade component 505 (e.g., storage bladeor the like network memory managing system). The mobile core component503 can operate with the radio access network or communication network502, and is configured to control the sessions, authentication, packetforwarding, etc. The mobile packet core component 503 includes a storageblade, which can also be communicatively coupled into the RAN 502, whichcan provide opportunities for mobile delivery diversity so the packetdata can be a part of the mobile packet core 503 for specific deliverytime, delivery based on some special triggers, or events, and so on.

Further, the access network discovery and selection function server 508can create one or more traffic steering rules when a new subscription iscreated, when a subscription is modified, when a user equipment devicelocation changes, application settings, triggers events are modified, UEparameters change and so forth. Thus, access network discovery andselection function server 508 can create and/or modify traffic steeringrules and store the traffic steering rules in one or more data stores510 (e.g., a library) for future use. The NOSA manager component 501 canbe further configured to communicate these rules, policies, or resourcesavailable to the application 522. The application 522 can be haltedbased on a trigger event occur, which can include an inadequate resourceor an expectation of inadequate resource from a particular network basedon UE parameters (speed, movement direction, location, accelerometerdata, etc.). The NOSA manager component 501 can modify the applicationsettings 524 in anticipation of the application 522 operating at adifferent level or different data delivery option, which can be for aperiod of time, indefinitely, or a specified delivery time, according toa trigger event.

The trigger events can be specified by the application 522 or theserving network 506 and tagged by a tagging component 516 of the NOSAmanger component 501. The tagging component 516 can be configured to setor assign different priorities to different triggers according to thepolicy component 514. For example, caching functions, segmentation andpacket reassembly, time shifting of certain packet flows can beconsidered or tagged in order accommodate load balancing requirementswith the application 522 and the network devices. Thus, the NOSA managercomponent 501 can control tagging mechanisms via the tagging component516 that enables such functions inside the networks 502. In one example,the UE device or application 522 on the UE device can initiate the dataflow that has some policies associated with it via the policy component514 being initiated at home, but as the UE device moves, such as withina car or moves at a faster speed thereby changing the UE parametersascertained by the UE parameter component 523, networks could be changedfrom a trigger event being communicated to the network. In addition,network conditions and load and congestion policies could be changed bythe network and/or the application settings. These policies could betagged and/or changed as these conditions change by the NOSA mangercomponent 501. The NOSA manger component 501 is configured to know whatthe critical packets or critical data packet units are for data deliveryand can monitor network resources available via the probe component 518to make sure those get delivered, by signaling network devices, UEparameters and application demands (application settings), in order tomake delivery continuous and maintain a quality of experience as thesedata flows are communicated with the network dynamics.

In another example, the storage blade component 505 or other networkattached storage to the mobile packet core component 503 and/or RANenvironment operates to perform according to the tags of the taggingcomponent 516, in which the tags can operate as stop signs on thenetwork when the receiver or transceiver 504 is not ready or when thedata is not properly formed, formatted/shaped or aggregated for properdelivery. For example, the data of the application 522 can be halteduntil an aggregation of data occurs, and then delivery in theappropriate setting or manner by the NOSA manger component 501 and tothe storage blade component 505 for proper delivery or packet flow inreal time with caching, network attached storage (NAS) and the like thatis aware of the application demands according to a data flow policy oroption.

For example, an application could be operating on a UE device by doingsocial networking or trying to collect data from the server, in which atrigger could be tagged or a set of application settings having certainnetwork demands via the tagging component 516. The trigger coulddesignated whoever has a highest priority as soon as his work convenes,then the application 522 could trigger that the data aggregation iscomplete and the results are to be shared, rather than constantlysharing data as it is received. In addition, the triggers or eventscould be requested from inside the application, where the applicationsays start gathering what everyone is thinking on this vote, until theone person provides his or her votes, a certain machine or other UEdevice returns votes, or a predefined time elapses, until then continuecollecting information within this social environment within aparticular data stream until a certain event/trigger happens. A trigger,for example, could be a period of time, someone else's action or anyother event. Applications can define their own triggers that initiatedata delivery such as to continue collecting data, operate another taskinside network or application, halt delivery to any UE device untilanother UE is close enough from a GPS perspective or other geographicallocation sensed to initiate a trigger for data delivery based onavailable network resources or devices. In addition, a network can havetriggers set or tagged for application 522. For example, a Wi-Fi networkcould have sixty triggers that are discoverable by the application. Inaddition, the UE device enter onto a San Francisco street network thathas another set of triggers discoverable by the same app. Thus, the UEcan tag certain triggers from the network or the application, activateor handle different triggers based on the UE or application demands.

In some implementations, access network discovery and selection functionserver 508 can communicate traffic steering policies to the UE device(e.g., UE device 201 of FIG. 2, or other UE device communicativelycoupled to the components of FIG. 5). In one aspect, access networkdiscovery and selection function server 508 can assist the UE device indiscovery of non-third generation partnership project access networks(e.g., Wi-Fi or worldwide interoperability for microwave access). Inanother aspect, access network discovery and selection function server508 can select appropriate traffic steering policies for a userequipment device and issue the policies. In one aspect, access networkdiscovery and selection function server 508 selects the traffic steeringrule based on the policies associated with the UE device via the policycomponent or application 522 such as a user subscription, a useraccount, or other classification associated with a UE device. In anotheraspect, access network discovery and selection function server 508communicates the appropriate traffic steering policy over acommunication framework. In an aspect, access network discovery andselection function server 508 can communicate directly with UE devicesthrough a server to client connection (e.g., standard S14 interface).However, access network discovery and selection function server 508 cancommunicate with UE devices through an indirect connection, a cellularbroadcast, and the like, in accordance with some implementations.

The policy information provided by the access network discovery andselection function server 508 can be retained in the one or more datastores 510, the storage blade component 505, or by the policy component514. According to an implementation, one or more data stores 510 can beintegrated with the NOSA manger component 501, the other componentcoupled there, and/or memory 202. In another implementation, one or moredata stores 510 can be located external to, but accessible by, the NOSAmanger component 501, the other component coupled there, and/or memory202.

The evaluation manager component 206 can to receive information relatedto the user equipment device and operate in conjunction with the NOSAmanger component 50. For example, usage of the UE device can be receivedby the evaluation manager component 206. The usage can indicate how thedevice is being used (e.g., voice call, data call, streaming video,surfing the Internet, and so forth). The usage can also indicate theapplications being executed on the user equipment device, wherein morethan one application might be executing at any particular time. Someapplications might perform better (e.g., have a better connectivity)with a cellular network and other applications might perform as expectedon either a cellular network or a Wi-Fi network. According to animplementation, traffic flows of the user equipment device can be splitbetween radio networks as discussed herein.

Other information related to the user equipment device and received bythe evaluation manager component 206 can be one or more mobilityparameters of the user equipment device. A mobility parameter can relateto whether the user equipment device is stationary or is moving and, ifmoving a speed at which the user equipment device is being moved. Forexample, the user equipment device might be stationary (e.g., a user ofthe user equipment device is sitting at her desk). In another example,the user equipment device might be moved and traveling at differentspeeds, which can be a function of the mode of transportation (e.g.,walking, riding a bicycle, in a car, on a train, in an airplane, and soon).

Another parameter relates to the direction that the user equipmentdevice is being moved. The direction can be a horizontal direction,which can be associated with cardinal directions or cardinal points(e.g., north, south, east, west, or intermediate points). Further, thedirection can include an altitude (or changes in the height) of the userequipment device. For example, the user equipment device might betraveling in an elevator and a range of one network might not reach allpoints along that altitude (e.g., connectivity is only enabled at thehigher locations).

An analysis component 512 can be configured to compare the informationrelated to the networks and the information related to the userequipment device. For example, if a network has a congestion conditionthat is near, or approaching, a maximum congestion level, that networkmight be removed from consideration. In another example, if the userequipment device is being moved toward a network, the evaluation managercomponent 206 and/or analysis component 512 can take into considerationthe movement of the user equipment device and might give moreconsideration to the one or more networks that are expected to belocated along the movement path of the user equipment device.

A policy component 514 can be configured to review the recommendationprovided by the analysis component 512 and determine if the selectednetwork complies with the access network discovery and selectionfunction policy of the serving network 506. According to some aspects,the policy component 514 ascertains whether a network conforms to thepolicy, which could be a set of application settings or demands, beforethe analysis component 512 analyzes the information related to thenetwork. Thus, if a particular network does not conform to the policy,that particular network is not considered by the analysis component 512.Further, information related to that network is not obtained (or isdisregarded if such information is obtained).

Based on the recommendation of the analysis component 512, a selectionmanager component 208 can determine to which radio technology or radionetwork (e.g., set of network devices) the network traffic of the userequipment device should be routed, or select from options that arecommunicated via the data delivery component 520 for different networkdelivery options or networks available (e.g., 3GPP, 4GPP, Wi-Fi, Femtocell, Macro cell, etc.). For example, the comparison by the analysiscomponent 512 might reveal that although various networks could properlyservice the user equipment device, based on user preferences, onlycellular networks should be used, which can be based on a pricing engineor billing tier, or other events being tagged. In another example, thenetworks could service the UE and the application based on userpreferences, application settings etc. according to one or more triggersinitiating a set of tags for one or more sets of application settings,in which Wi-Fi networks should be used, where feasible or other datadelivery option comprising one or more storage options, packet flows, orother resource considerations. In a further example, based on anapplication (or multiple applications) executing on the user equipmentdevice, a particular radio technology (or more than one radiotechnology) can be selected for at least a portion of the user traffic.

A routing manager component 210 provides the appropriate signaling tothe source network and the target network in order to route at least aportion of the network traffic of the user equipment device to theselected network. Such signaling can utilize various types of signalingas a function of the network types and other parameters.

In another embodiment, the application services and API manger 218 canfurther be configured to operate a scalable application level controlring that operates as a network level ring. The network level ringanalyzes the tags of the tagging component 516, which can be set by theNOSA manger component 501 or NOSA kernel. The network level ring of theapplication services and API manager 218 can function as another layeron top of the existing switches or routing devices for providing routingin consideration of the tags related to the application settings, or thedata delivery options for a set of radio network options (performanceoptions). The tags could be set for different subsets of applicationssettings to be triggered according to event triggers specified in theapplication settings or by a particular network. The data deliveryoptions can be based on a data delivery trigger occurring to satisfy adata delivery that is controlled or selected by the applicationperformance or demand level specified by the set of applicationsettings. The application services and API manger 218 can thereforecontrol the application level control ring and switch networks, orselect other data delivery options by specifying the network or otherradio network performance settings for network resources. The datadelivery options can comprise a different network device option thatselects a different network device of the self-organizing networkdevices to deliver data than a current network device (e.g., from acellular network device to a Wi-Fi network device). The data deliveryoptions can include a network observed signaling data representing asignaling of the set of self-organizing network devices associated witha network device option of the set (e.g., packet priority, time shiftingfunctions, signal threshold levels, storage management processesavailable, etc.). The application services and API manager 218 can thuscommunicate to underlying switches of routers in the network theapplication level ring with tag information for particular applicationsoperating on the UE for the router devices or network devices toconsider along with other tags and switching concepts for networkoperation. For example, the application services and API manager 218 canprovide another level of routing, switching and aggregation at thetransport layer and up before data is processed back down forcommunications.

While the methods described within this disclosure are illustrated inand described herein as a series of acts or events, it will beappreciated that the illustrated ordering of such acts or events are notto be interpreted in a limiting sense. For example, some acts may occurin different orders and/or concurrently with other acts or events apartfrom those illustrated and/or described herein. In addition, not allillustrated acts may be required to implement one or more aspects orembodiments of the description herein. Further, one or more of the actsdepicted herein may be carried out in one or more separate acts and/orphases. Reference may be made to the figures described above for ease ofdescription. However, the methods are not limited to any particularembodiment or example provided within this disclosure and can be appliedto any of the systems disclosed herein.

FIG. 6 illustrates an example, non-limiting method 600 for routingnetwork traffic, according to an aspect. At 602, network congestionconditions and network parameter conditions related to two or morecommunications networks are compared with a usage and a movementparameter of the mobile device and considering the application settingsfor particular applications managed by a UE device. The networkcongestion conditions and network parameter conditions can be receivedfrom respective networks (e.g., respective sets of network devicesincluded in each network). The usage and movement parameter of themobile device can be obtained internally from the mobile device andapplication settings from the application via one or more componentsdiscussed above.

At 604, a determination is made as to a radio performance settingsassociated with at least one of the set of network devices to which atleast a portion of the network traffic of the mobile device can berouted or is currently operating data delivery. The determination caninclude considerations related to adhering to the discovery informationand selection policies associated with a set of network devices of aserving network (e.g., source network). For example, if a particularnetwork is not an appropriate network according to the discoveryinformation and selection policies (e.g., groups or subsets ofapplications settings based on one or more tags for trigger events),then that network is removed from consideration or the applicationsetting themselves could be modified.

Network traffic of the mobile device is routed, at 606, to the selectedset of network devices for different radio network performance settings.According to some aspects, a portion of the network traffic of themobile device can be routed to a first set of network devices associatedwith a first radio technology and another portion of the network trafficof the mobile device is routed to a second set of network devicesassociated with a second radio technology. For example, traffic flows ofthe mobile device can be split between the first set of network devicesand the second set of network devices based on one or more applicationfunctions or processes being initiated.

FIG. 7 illustrates an example, non-limiting method 700, according to anaspect. At 702, a device (e.g., NOSA manger or kernel) comprising aprocessor facilitates a communication to a network device and a mangerserver of a set of self-organizing network devices to exchange a set ofcontexts between an application managed by a user equipment device andthe network device.

At 704, the device extends the set of self-organizing devices to becontext aware of the application and the network device.

At 706, in response to detecting the user equipment device communicatingvia the set of self-organizing network devices, communicating, by thedevice, to the application and the user equipment device and obtaining,by the device, a set of user equipment device parameters and a set ofapplication settings of the application.

At 708, modifying, by the device, a set of radio network performancesettings of the set of self-organizing network devices with the userequipment device based on the set of user equipment device parametersand the set of application settings of the application.

The set of user equipment device parameters can comprise user equipmentsensed data related to the user equipment device, such as by one or moresensors on the UE device, for example. The user equipment sensed datacomprises accelerometer data, battery power data, speed data, directiondata, network observed signaling data representing a signaling of theset of self-organizing network devices, load data representing a load ofthe set of self-organizing network devices, and congestion datarepresenting a congestion of the set of self-organizing network devices.

The radio network performance settings can include load, congestion,time shifting, prioritization policies, a bandwidth, speed, a networkselection, load, and forward functions of the networks that can beprovided for the application as resources available, for example. Thenetwork performance settings can includes sets of performance parametersas discussed herein available from SON devices within the area orlocation of the UE device based on the UE parameters ascertained, forexample, such as network congestion conditions, and other networkparameters associated with one or more different network devices asdiscussed above.

FIG. 8 illustrates another example, non-limiting embodiment of a processflow 800. At 802, a device (e.g., NOSA manger or kernel) comprising aprocessor facilitates a communication to a network device of a set ofself-organizing network devices to exchange a set of contexts between anapplication managed by a user equipment device and the network device.

At 804, in response to detecting the user equipment device communicatingvia the set of self-organizing network devices, communicating a set ofapplication settings that include a set of data delivery triggersassociated with the application and a set of user equipment deviceparameters associated with the user equipment device.

At 806, in response to detecting the user equipment device communicatingvia the set of self-organizing network devices, communicating a set ofdata delivery options from the network device of the set ofself-organizing network devices to the user equipment device based onthe set of application settings and the set of user equipment deviceparameters.

In one embodiment, the method can further include selecting a datadelivery option of the set of data delivery options based on a datadelivery trigger occurring to satisfy a data delivery specified by theset of application settings. The data delivery options, for example, cancomprise a different network device option for the different networkdevice of the self-organizing network devices to deliver data, networkobserved signaling data representing a signaling of the set ofself-organizing network devices associated with a network device optionof the set of self-organizing network devices, load data representing aload of the set of self-organizing network devices, and congestion datarepresenting a congestion of the set of self-organizing network devices.

By way of further description with respect to one or more non-limitingways to facilitate network traffic routing selection, FIG. 9 is aschematic example wireless environment 900 that can operate inaccordance with aspects described herein. In particular, examplewireless environment 900 illustrates a set of wireless network macrocells. Three coverage macro cells 902, 904, and 906 include theillustrative wireless environment; however, it is noted that wirelesscellular network deployments can encompass any number of macro cells.Coverage macro cells 902, 904, and 906 are illustrated as hexagons;however, coverage cells can adopt other geometries generally dictated bya deployment configuration or floor plan, geographic areas to becovered, and so on. Each macro cell 902, 904, and 906 is sectorized in a2π/3 configuration in which each macro cell includes three sectors,demarcated with dashed lines in FIG. 9. It is noted that othersectorizations are possible, and aspects or features of the disclosedsubject matter can be exploited regardless of type of sectorization.Macro cells 902, 904, and 906 are served respectively through basestations or eNodeBs 908, 910, and 912. Any two eNodeBs can be consideredan eNodeB site pair. It is noted that radio component(s) arefunctionally coupled through links such as cables (e.g., RF andmicrowave coaxial lines), ports, switches, connectors, and the like, toa set of one or more antennas that transmit and receive wireless signals(not illustrated). It is noted that a radio network controller (notshown), which can be a part of mobile network platform(s) 914, and setof base stations (e.g., eNode B 908, 910, and 912) that serve a set ofmacro cells; electronic circuitry or components associated with the basestations in the set of base stations; a set of respective wireless links(e.g., links 916, 918, and 920) operated in accordance to a radiotechnology through the base stations, form a macro radio access network.It is further noted that, based on network features, the radiocontroller can be distributed among the set of base stations orassociated radio equipment. In an aspect, for universal mobiletelecommunication system-based networks, wireless links 916, 918, and920 embody a Uu interface (universal mobile telecommunication system AirInterface).

Mobile network platform(s) 914 facilitates circuit switched-based (e.g.,voice and data) and packet-switched (e.g., Internet protocol, framerelay, or asynchronous transfer mode) traffic and signaling generation,as well as delivery and reception for networked telecommunication, inaccordance with various radio technologies for disparate markets.Telecommunication is based at least in part on standardized protocolsfor communication determined by a radio technology utilized forcommunication. In addition, telecommunication can exploit variousfrequency bands, or carriers, which include any electromagneticfrequency bands licensed by the service provider network 922 (e.g.,personal communication services, advanced wireless services, generalwireless communications service, and so forth), and any unlicensedfrequency bands currently available for telecommunication (e.g., the 2.4GHz industrial, medical and scientific band or one or more of the 5 GHzset of bands). In addition, mobile network platform(s) 914 can controland manage base stations 908, 910, and 912 and radio component(s)associated thereof, in disparate macro cells 902, 904, and 906 by wayof, for example, a wireless network management component (e.g., radionetwork controller(s), cellular gateway node(s), etc.). Moreover,wireless network platform(s) can integrate disparate networks (e.g.,Wi-Fi network(s), femto cell network(s), broadband network(s), servicenetwork(s), enterprise network(s), and so on). In cellular wirelesstechnologies (e.g., third generation partnership project universalmobile telecommunication system, global system for mobile communication,mobile network platform 914 can be embodied in the service providernetwork 922.

In addition, wireless backhaul link(s) 924 can include wired linkcomponents such as T1/E1 phone line; T3/DS3 line, a digital subscriberline either synchronous or asynchronous; an asymmetric digitalsubscriber line; an optical fiber backbone; a coaxial cable, etc.; andwireless link components such as line-of-sight or non-line-of-sightlinks which can include terrestrial air-interfaces or deep space links(e.g., satellite communication links for navigation). In an aspect, foruniversal mobile telecommunication system-based networks, wirelessbackhaul link(s) 924 embodies IuB interface.

It is noted that while exemplary wireless environment 900 is illustratedfor macro cells and macro base stations, aspects, features andadvantages of the disclosed subject matter can be implemented in microcells, pico cells, femto cells, or the like, wherein base stations areembodied in home-based equipment related to access to a network.

To provide further context for various aspects of the disclosed subjectmatter, FIG. 10 illustrates a block diagram of an embodiment of accessequipment and/or software 1000 related to access of a network (e.g.,base station, wireless access point, femtocell access point, and soforth) that can enable and/or exploit features or aspects of thedisclosed aspects.

Access equipment and/or software 1000 related to access of a network canreceive and transmit signal(s) from and to wireless devices, wirelessports, wireless routers, etc. through segments 1002 ₁-1002 _(B) (B is apositive integer). Segments 1002 ₁-1002 _(B) can be internal and/orexternal to access equipment and/or software 1000 related to access of anetwork, and can be controlled by a monitor component 1004 and anantenna component 1006. Monitor component 1004 and antenna component1006 can couple to communication platform 1008, which can includeelectronic components and associated circuitry that provide forprocessing and manipulation of received signal(s) and other signal(s) tobe transmitted.

In an aspect, communication platform 1008 includes areceiver/transmitter 1010 that can convert analog signals to digitalsignals upon reception of the analog signals, and can convert digitalsignals to analog signals upon transmission. In addition,receiver/transmitter 1010 can divide a single data stream into multiple,parallel data streams, or perform the reciprocal operation. Coupled toreceiver/transmitter 1010 can be a multiplexer/demultiplexer 1012 thatcan facilitate manipulation of signals in time and frequency space.Multiplexer/demultiplexer 1012 can multiplex information (data/trafficand control/signaling) according to various multiplexing schemes such astime division multiplexing, frequency division multiplexing, orthogonalfrequency division multiplexing, code division multiplexing, spacedivision multiplexing. In addition, multiplexer/demultiplexer component1012 can scramble and spread information (e.g., codes, according tosubstantially any code known in the art, such as Hadamard-Walsh codes,Baker codes, Kasami codes, polyphase codes, and so forth).

A modulator/demodulator 1014 is also a part of communication platform1008, and can modulate information according to multiple modulationtechniques, such as frequency modulation, amplitude modulation (e.g.,M-ary quadrature amplitude modulation, with M a positive integer);phase-shift keying; and so forth).

Access equipment and/or software 1000 related to access of a networkalso includes a processor 1016 configured to confer, at least in part,functionality to substantially any electronic component in accessequipment and/or software 1000. In particular, processor 1016 canfacilitate configuration of access equipment and/or software 1000through, for example, monitor component 1004, antenna component 1006,and one or more components therein. Additionally, access equipmentand/or software 1000 can include display interface 1018, which candisplay functions that control functionality of access equipment and/orsoftware 1000, or reveal operation conditions thereof. In addition,display interface 1018 can include a screen to convey information to anend user. In an aspect, display interface 1018 can be a liquid crystaldisplay, a plasma panel, a monolithic thin-film based electrochromicdisplay, and so on. Moreover, display interface 1018 can include acomponent (e.g., speaker) that facilitates communication of auralindicia, which can also be employed in connection with messages thatconvey operational instructions to an end user. Display interface 1018can also facilitate data entry (e.g., through a linked keypad or throughtouch gestures), which can cause access equipment and/or software 1000to receive external commands (e.g., restart operation).

Broadband network interface 1020 facilitates connection of accessequipment and/or software 1000 to a service provider network (not shown)that can include one or more cellular technologies (e.g., thirdgeneration partnership project universal mobile telecommunicationsystem, global system for mobile communication, and so on) throughbackhaul link(s) (not shown), which enable incoming and outgoing dataflow. Broadband network interface 1020 can be internal or external toaccess equipment and/or software 1000, and can utilize display interface1018 for end-user interaction and status information delivery.

Processor 1016 can be functionally connected to communication platform1008 and can facilitate operations on data (e.g., symbols, bits, orchips) for multiplexing/demultiplexing, such as effecting direct andinverse fast Fourier transforms, selection of modulation rates,selection of data packet formats, inter-packet times, and so on.Moreover, processor 1016 can be functionally connected, through data,system, or an address bus 1022, to display interface 1018 and broadbandnetwork interface 1020, to confer, at least in part, functionality toeach of such components.

In access equipment and/or software 1000, memory 1024 can retainlocation and/or coverage area (e.g., macro sector, identifier(s)) accesslist(s) that authorize access to wireless coverage through accessequipment and/or software 1000, sector intelligence that can includeranking of coverage areas in the wireless environment of accessequipment and/or software 1000, radio link quality and strengthassociated therewith, or the like. Memory 1024 also can store datastructures, code instructions and program modules, system or deviceinformation, code sequences for scrambling, spreading and pilottransmission, access point configuration, and so on. Processor 1016 canbe coupled (e.g., through a memory bus), to memory 1024 in order tostore and retrieve information used to operate and/or conferfunctionality to the components, platform, and interface that residewithin access equipment and/or software 1000.

As it employed in the subject specification, the term “processor” canrefer to substantially any computing processing unit or deviceincluding, but not limited to including, single-core processors;single-processors with software multithread execution capability;multi-core processors; multi-core processors with software multithreadexecution capability; multi-core processors with hardware multithreadtechnology; parallel platforms; and parallel platforms with distributedshared memory. Additionally, a processor can refer to an integratedcircuit, an application specific integrated circuit, a digital signalprocessor, a field programmable gate array, a programmable logiccontroller, a complex programmable logic device, a discrete gate ortransistor logic, discrete hardware components, or any combinationthereof designed to perform the functions and/or processes describedherein. Processors can exploit nano-scale architectures such as, but notlimited to, molecular and quantum-dot based transistors, switches andgates, in order to optimize space usage or enhance performance of mobiledevices. A processor may also be implemented as a combination ofcomputing processing units.

In the subject specification, terms such as “store,” “data store,” datastorage,” “database,” and substantially any other information storagecomponent relevant to operation and functionality of a component and/orprocess, refer to “memory components,” or entities embodied in a“memory,” or components including the memory. It is noted that thememory components described herein can be either volatile memory ornonvolatile memory, or can include both volatile and nonvolatile memory.

By way of illustration, and not limitation, nonvolatile memory, forexample, can be included in memory 1024, non-volatile memory (seebelow), disk storage (see below), and memory storage (see below).Further, nonvolatile memory can be included in read only memory,programmable read only memory, electrically programmable read onlymemory, electrically erasable programmable read only memory, or flashmemory. Volatile memory can include random access memory, which acts asexternal cache memory. By way of illustration and not limitation, randomaccess memory is available in many forms such as synchronous randomaccess memory, dynamic random access memory, synchronous dynamic randomaccess memory, double data rate synchronous dynamic random accessmemory, enhanced synchronous dynamic random access memory, Synchlinkdynamic random access memory, and direct Rambus random access memory.Additionally, the disclosed memory components of systems or methodsherein are intended to include, without being limited to including,these and any other suitable types of memory.

In order to provide a context for the various aspects of the disclosedsubject matter, FIG. 11, and the following discussion, are intended toprovide a brief, general description of a suitable environment in whichthe various aspects of the disclosed subject matter can be implemented.While the subject matter has been described above in the general contextof computer-executable instructions of a computer program that runs on acomputer and/or computers, those skilled in the art will recognize thatthe various aspects also can be implemented in combination with otherprogram modules. Generally, program modules include routines, programs,components, data structures, etc. that performs particular tasks and/orimplement particular abstract data types. For example, in memory therecan be software, which can instruct a processor to perform variousactions. The processor can be configured to execute the instructions inorder to implement the analysis of monitoring an uplink power level,detecting the uplink power level is at or above a threshold level,and/or disable transmission of at least one message as a result of themonitored uplink power level.

Moreover, those skilled in the art will understand that the variousaspects can be practiced with other computer system configurations,including single-processor or multiprocessor computer systems,mini-computing devices, mainframe computers, as well as personalcomputers, base stations hand-held computing devices or user equipment,such as a tablet, phone, watch, and so forth, processor-basedcomputers/systems, microprocessor-based or programmable consumer orindustrial electronics, and the like. The illustrated aspects can alsobe practiced in distributed computing environments where tasks areperformed by remote processing devices that are linked through acommunications network; however, some if not all aspects of the subjectdisclosure can be practiced on stand-alone computers. In a distributedcomputing environment, program modules can be located in both local andremote memory storage devices.

With reference to FIG. 11, a block diagram of a computing system 1100operable to execute the disclosed systems and methods is illustrated, inaccordance with an embodiment. Computer 1102 includes a processing unit1104, a system memory 1106, and a system bus 1108. System bus 1108couples system components including, but not limited to, system memory1106 to processing unit 1104. Processing unit 1104 can be any of variousavailable processors. Dual microprocessors and other multiprocessorarchitectures also can be employed as processing unit 1104.

System bus 1108 can be any of several types of bus structure(s)including a memory bus or a memory controller, a peripheral bus or anexternal bus, and/or a local bus using any variety of available busarchitectures including, but not limited to, industrial standardarchitecture, micro-channel architecture, extended industrial standardarchitecture, intelligent drive electronics, video electronics standardsassociation local bus, peripheral component interconnect, card bus,universal serial bus, advanced graphics port, personal computer memorycard international association bus, Firewire and small computer systemsinterface.

System memory 1106 includes volatile memory 1110 and nonvolatile memory1112. A basic input/output system, containing routines to transferinformation between elements within computer 1102, such as duringstart-up, can be stored in nonvolatile memory 1112. By way ofillustration, and not limitation, nonvolatile memory 1112 can includeread only memory, programmable read only memory, electricallyprogrammable read only memory, electrically erasable programmable readonly memory, or flash memory. Volatile memory 1110 can include randomaccess memory, which acts as external cache memory. By way ofillustration and not limitation, random access memory is available inmany forms such as dynamic random access memory, synchronous randomaccess memory, synchronous dynamic random access memory, double datarate synchronous dynamic random access memory, enhanced synchronousdynamic random access memory, Synchlink dynamic random access memory,and direct Rambus random access memory, direct Rambus dynamic randomaccess memory, and Rambus dynamic random access memory.

Computer 1102 also includes removable/non-removable,volatile/non-volatile computer storage media. In an implementation,provided is a non-transitory or tangible computer-readable mediumstoring executable instructions that, in response to execution, cause asystem comprising a processor to perform operations. The operations caninclude comparing a first network congestion condition and a firstnetwork parameter condition received from a first set of network devicesof a first network, and a second network congestion condition and asecond network parameter condition received from a second set of networkdevices of a second network to a usage parameter and a movementparameter of a mobile device. The operations can also includedetermining a radio technology (e.g., radio network device) to which toroute network traffic of the mobile device. Determining the routing ofthe network traffic can include, based on a first outcome of thecomparing, determining to route the network traffic to the first set ofnetwork devices associated with a first radio technology. In anotherexample, determining the routing of the network traffic can include,based on a second outcome of the comparing, determining to route thenetwork traffic of the mobile device to the second set of networkdevices associated with a second radio technology. In an implementation,determining the set of network devices can include complying with anetwork selection policy received from a network device that provides aservice to the mobile device. Further, the operations can includefacilitating routing of the network traffic of the mobile device to theset of network devices.

In an implementation, the operations can include analyzing relativemovement of the mobile device with respect to the first set of networkdevices and the second set of network devices. According to anotherimplementation, the operations can include determining speed datarepresenting a substantially current speed of the mobile device anddirection data representing a substantially current direction of themobile device.

FIG. 11 illustrates, for example, disk storage 1114. Disk storage 1114includes, but is not limited to, devices such as a magnetic disk drive,floppy disk drive, tape drive, external or internal removable storagedrives, super disk drive, flash memory card, or memory stick. Inaddition, disk storage 1114 can include storage media separately or incombination with other storage media including, but not limited to, anoptical disk drive such as a compact disk read only memory device,compact disk recordable drive, compact disk rewritable drive or adigital versatile disk read only memory drive. To facilitate connectionof the disk storage 1114 to system bus 1108, a removable ornon-removable interface is typically used, such as interface component1116.

It is to be noted that FIG. 11 describes software that acts as anintermediary between users and computer resources described in suitableoperating environment. Such software includes an operating system 1118.Operating system 1118, which can be stored on disk storage 1114, acts tocontrol and allocate resources of computer system 1102. Systemapplications 1120 can take advantage of the management of resources byoperating system 1118 through program modules 1122 and program data 1124stored either in system memory 1106 or on disk storage 1114. It is to beunderstood that the disclosed subject matter can be implemented withvarious operating systems or combinations of operating systems.

A user can enter commands or information, for example through interfacecomponent 1116, into computer system 1102 through input device(s) 1126.Input devices 1126 include, but are not limited to, a pointing devicesuch as a mouse, trackball, stylus, touch pad, keyboard, microphone,joystick, game pad, satellite dish, scanner, TV tuner card, digitalcamera, digital video camera, web camera, and the like. These and otherinput devices connect to processing unit 1104 through system bus 1108through interface port(s) 1128. Interface port(s) 1128 include, forexample, a serial port, a parallel port, a game port, and a universalserial bus. Output device(s) 1130 use some of the same type of ports asinput device(s) 1126.

Thus, for example, a universal serial bus port can be used to provideinput to computer 1102 and to output information from computer 1102 toan output device 1130. Output adapter 1132 is provided to illustratethat there are some output devices 1130, such as monitors, speakers, andprinters, among other output devices 1130, which use special adapters.Output adapters 1132 include, by way of illustration and not limitation,video and sound cards that provide means of connection between outputdevice 1130 and system bus 1108. It is also noted that other devicesand/or systems of devices provide both input and output capabilitiessuch as remote computer(s) 1134.

Computer 1102 can operate in a networked environment using logicalconnections to one or more remote computers, such as remote computer(s)1134. Remote computer(s) 1134 can be a personal computer, a server, arouter, a network computer, a workstation, a microprocessor basedappliance, a peer device, or other common network node and the like, andtypically includes many or all of the elements described relative tocomputer 1102.

For purposes of brevity, only one memory storage device 1136 isillustrated with remote computer(s) 1134. Remote computer(s) 1134 islogically connected to computer 1102 through a network interface 1138and then physically connected through communication connection 1140.Network interface 1138 encompasses wire and/or wireless communicationnetworks such as local area networks and wide area networks. Local areanetwork technologies include fiber distributed data interface, copperdistributed data interface, Ethernet, token ring and the like. Wide areanetwork technologies include, but are not limited to, point-to-pointlinks, circuit switching networks, such as integrated services digitalnetworks and variations thereon, packet switching networks, and digitalsubscriber lines.

Communication connection(s) 1140 refer(s) to hardware/software employedto connect network interface 1138 to system bus 1108. Whilecommunication connection 1140 is shown for illustrative clarity insidecomputer 1102, it can also be external to computer 1102. Thehardware/software for connection to network interface 1138 can include,for example, internal and external technologies such as modems,including regular telephone grade modems, cable modems and DSL modems,ISDN adapters, and Ethernet cards.

It is to be noted that aspects, features, or advantages of the aspectsdescribed in the subject specification can be exploited in substantiallyany communication technology. For example, 4G technologies, Wi-Fi,worldwide interoperability for microwave access, Enhanced gatewaygeneral packet radio service, third generation partnership project longterm evolution, third generation partnership project 2 ultra-mobilebroadband, third generation partnership project universal mobiletelecommunication system, high speed packet access, high-speed downlinkpacket access, high-speed uplink packet access, global system for mobilecommunication edge radio access network, universal mobiletelecommunication system terrestrial radio access network, long termevolution advanced. Additionally, substantially all aspects disclosedherein can be exploited in legacy telecommunication technologies; e.g.,global system for mobile communication. In addition, mobile as wellnon-mobile networks (e.g., Internet, data service network such asInternet protocol television) can exploit aspect or features describedherein.

Various aspects or features described herein can be implemented as amethod, apparatus, or article of manufacture using standard programmingand/or engineering techniques. In addition, various aspects disclosed inthe subject specification can also be implemented through programmodules stored in a memory and executed by a processor, or othercombination of hardware and software, or hardware and firmware.

Other combinations of hardware and software or hardware and firmware canenable or implement aspects described herein, including the disclosedmethod(s). The term “article of manufacture” as used herein is intendedto encompass a computer program accessible from any computer-readabledevice, carrier, or media. For example, computer readable media caninclude but are not limited to magnetic storage devices (e.g., harddisk, floppy disk, magnetic strips . . . ), optical discs (e.g., compactdisc, digital versatile disc, blu-ray disc . . . ), smart cards, andflash memory devices (e.g., card, stick, key drive . . . ).

Computing devices typically include a variety of media, which caninclude computer-readable storage media or communications media, whichtwo terms are used herein differently from one another as follows.

Computer-readable storage media can be any available storage media thatcan be accessed by the computer and includes both volatile andnonvolatile media, removable and non-removable media. By way of example,and not limitation, computer-readable storage media can be implementedin connection with any method or technology for storage of informationsuch as computer-readable instructions, program modules, structureddata, or unstructured data. Computer-readable storage media can include,but are not limited to, random access memory, read only memory,electrically erasable programmable read only memory, flash memory orother memory technology, compact disk read only memory, digitalversatile disk or other optical disk storage, magnetic cassettes,magnetic tape, magnetic disk storage or other magnetic storage devices,or other tangible and/or non-transitory media which can be used to storedesired information. Computer-readable storage media can be accessed byone or more local or remote computing devices, e.g., via accessrequests, queries or other data retrieval protocols, for a variety ofoperations with respect to the information stored by the medium.

Communications media typically embody computer-readable instructions,data structures, program modules or other structured or unstructureddata in a data signal such as a modulated data signal, e.g., a carrierwave or other transport mechanism, and includes any information deliveryor transport media. The term “modulated data signal” or signals refersto a signal that has one or more of its characteristics set or changedin such a manner as to encode information in one or more signals. By wayof example, and not limitation, communication media include wired media,such as a wired network or direct-wired connection, and wireless mediasuch as acoustic, RF, infrared and other wireless media.

What has been described above includes examples of systems and methodsthat provide advantages of the one or more aspects. It is, of course,not possible to describe every conceivable combination of components ormethods for purposes of describing the aspects, but one of ordinaryskill in the art may recognize that many further combinations andpermutations of the claimed subject matter are possible. Furthermore, tothe extent that the terms “includes,” “has,” “possesses,” and the likeare used in the detailed description, claims, appendices and drawingssuch terms are intended to be inclusive in a manner similar to the term“comprising” as “comprising” is interpreted when employed as atransitional word in a claim.

As used in this application, the terms “component,” “system,” and thelike are intended to refer to a computer-related entity or an entityrelated to an operational apparatus with one or more specificfunctionalities, wherein the entity can be either hardware, acombination of hardware and software, software, or software inexecution. As an example, a component may be, but is not limited tobeing, a process running on a processor, a processor, an object, anexecutable, a thread of execution, computer-executable instructions, aprogram, and/or a computer. By way of illustration, both an applicationrunning on a server or network controller, and the server or networkcontroller can be a component. One or more components may reside withina process and/or thread of execution and a component may be localized onone computer and/or distributed between two or more computers. Also,these components can execute from various computer readable media havingvarious data structures stored thereon. The components may communicatevia local and/or remote processes such as in accordance with a signalhaving one or more data packets (e.g., data from one componentinteracting with another component in a local system, distributedsystem, and/or across a network such as the Internet with other systemsvia the signal). As another example, a component can be an apparatuswith specific functionality provided by mechanical parts operated byelectric or electronic circuitry, which is operated by a software, orfirmware application executed by a processor, wherein the processor canbe internal or external to the apparatus and executes at least a part ofthe software or firmware application. As yet another example, acomponent can be an apparatus that provides specific functionalitythrough electronic components without mechanical parts, the electroniccomponents can include a processor therein to execute software orfirmware that confers at least in part the functionality of theelectronic components. As further yet another example, interface(s) caninclude input/output components as well as associated processor,application, or application programming interface components.

The term “set”, “subset”, or the like as employed herein excludes theempty set (e.g., the set with no elements therein). Thus, a “set”,“subset”, or the like includes one or more elements or periods, forexample. As an illustration, a set of periods includes one or moreperiods; a set of transmissions includes one or more transmissions; aset of resources includes one or more resources; a set of messagesincludes one or more messages, and so forth.

In addition, the term “or” is intended to mean an inclusive “or” ratherthan an exclusive “or.” That is, unless specified otherwise, or clearfrom context, “X employs A or B” is intended to mean any of the naturalinclusive permutations. That is, if X employs A; X employs B; or Xemploys both A and B, then “X employs A or B” is satisfied under any ofthe foregoing instances. Moreover, articles “a” and “an” as used in thesubject specification and annexed drawings should generally be construedto mean “one or more” unless specified otherwise or clear from contextto be directed to a singular form.

What is claimed is:
 1. A system, comprising: a processor; and a memorythat stores executable instructions that, when executed by theprocessor, facilitate performance of operations, comprising: based onapplication context data associated with an application managed by amobile device, determining network context data associated with anetwork device, wherein the application context data is indicative of aprocess associated with the application, and wherein the network deviceis a device of self-organizing network devices of a communicationnetwork; and based on the network context data, directing delivery datafrom the network device to the mobile device, wherein the delivery datacomprises time shift data that is employable to delay a delivery ofcommunication data associated with the application.
 2. The system ofclaim 1, wherein the operations further comprise: based on deviceparameter data associated with the mobile device, modifying aperformance setting of the self-organizing network devices.
 3. Thesystem of claim 2, wherein the device parameter data comprises sensordata sensed via a sensor of the mobile device.
 4. The system of claim 2,wherein the device parameter data comprises battery power dataindicative of a power level of a battery of the mobile device.
 5. Thesystem of claim 2, wherein the device parameter data comprises speeddata indicative of a speed of the mobile device.
 6. The system of claim2, wherein the performance setting comprises a bandwidth associated withthe self-organizing network devices.
 7. The system of claim 2, whereinthe performance setting comprises a network congestion parameterassociated with the self-organizing network devices.
 8. The system ofclaim 1, wherein the delivery data comprises network observed signalingdata representing a signaling of the self-organizing network devices. 9.The system of claim 1, wherein the delivery data comprises load datarepresenting a load of the self-organizing network devices.
 10. Amethod, comprising: based on application context data associated with anapplication executed via a user equipment, determining, by a systemcomprising a processor, network context data associated with a networkdevice of self-organizing network devices of a communication network,wherein the application context data is associated with a thread of theapplication; and based on the network context data, initiating, by thesystem, a transfer of delivery data indicative of a delivery optioncomprising a time shifting parameter that is employable to delay atransfer of communication data that is to be transmitted from thenetwork device to the user equipment.
 11. The method of claim 10,wherein the initiating comprises initiating the transfer based on sensordata sensed via the user equipment.
 12. The method of claim 11, whereinthe initiating comprises initiating the transfer based on accelerometerdata sensed by an accelerometer of the user equipment.
 13. The method ofclaim 11, wherein the initiating comprises initiating the transfer basedon power data associated with a battery of the user equipment.
 14. Themethod of claim 11, wherein the initiating comprises initiating thetransfer based on network observed signaling data representing asignaling associated with the network device.
 15. The method of claim11, wherein the initiating comprises initiating the transfer of thedelivery data comprising profiling data that is employable to facilitateprofiling of the communication data.
 16. The method of claim 11, whereinthe initiating comprises initiating the transfer of the delivery datacomprising reprioritization data that is employable to facilitate packetreprioritization of data packets of the communication data.
 17. Anon-transitory machine-readable medium comprising executableinstructions that, when executed by a processor facilitate performanceof operations, comprising: based on application context data associatedwith an application of a user equipment, determining network contextdata associated with a network device of self-organizing network devicesof a communication network, wherein the application context data isassociated with a thread of the application; and based on the networkcontext data, directing, to the user equipment, delivery data comprisingtime shifting data that enables delaying a delivery of communicationdata associated with the application.
 18. The non-transitorymachine-readable medium of claim 17, wherein the operations furthercomprise: based on device parameter data associated with the userequipment, modifying a performance setting of the self-organizingnetwork devices.
 19. The non-transitory machine-readable medium of claim18, wherein the device parameter data comprises sensor data sensed via asensor of the user equipment.
 20. The non-transitory machine-readablemedium of claim 18, wherein the device parameter data comprises powerdata associated with a battery of the user equipment.